First the word script is not accurate, because some "scripts" will be one or more java classes. But the general idea is that these are "scripts" for adding new behavior to existing objects or components.

There are multiple types of scripting in OTrunk. To start with we'll make a scripting framework that makes it easy to explicity add to scripts objects, and then execute them in the views or controllers.

OTrunk Script Notes

Script Types

ot-view implementations

This type of scripting would be used to create a new view of an existing java object. This will become more important for reporting and logging. But right now it is easy enough to use Java for this.

ot-object lifecycle listeners

This type of scripting can respond to state changes in an ot-object, and then update another ot-object. This type of scripting will become more important as it is easier to build ot-classes which track the actual view classes. It requries making ot-classes with properties for every part of a component that needs to be scripted. And then keeping those properties synchronized with the component as it changes. When ot-view implementation scripting is feasible then this will be the preferred way of adding new behavior. It will be prefered because it will ensure that everything you want to respond to with scripts can be recorded for logging or reporting.

ot-view lifecycle listeners

This will be the first type of script to be implemented. Scripts of this type will have access to the ot-object being viewed, other views in a page or container, and the actual java objects used to render those views. This will make it easier to create any type of new behavior using existing ot-objects and ot-views. It will not ensure that the scriptable events will be logged however so it is not a good long term solution.
OTView Scripting